Accessing system user interfaces on an electronic device

ABSTRACT

In some embodiments, an electronic device in communication with a display and a touch-sensitive surface displays a user interface, and while displaying the user interface, the electronic device receives touch input comprising a contact detected on the touch-sensitive surface. In some embodiments, in response to receiving the touch input, and in accordance with a determination that the touch input satisfies first criteria, wherein the first criteria include a requirement that the contact continues to be detected in a predefined region of the touch-sensitive surface for longer than a time threshold, the electronic device displays a first indication that further input of a first type detected at the touch sensitive surface will cause the device to display a first system user interface. In some embodiments, in accordance with a determination that the touch input does not satisfy the first criteria, the electronic device forgoes displaying the first indication.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/146,594, filed Sep. 28, 2018 and published as U.S. Patent PublicationNo. 2019-0369861 on Dec. 5, 2019, which claims the benefit under 35 USC119(e) of U.S. Provisional Patent Application No. 62/679,503, filed Jun.1, 2018, the contents of both of which are incorporated herein byreference in their entirety for all purposes.

FIELD OF THE DISCLOSURE

This relates generally to electronic devices that allow access to systemuser interfaces, and user interactions with such devices.

BACKGROUND OF THE DISCLOSURE

User interaction with electronic devices has increased significantly inrecent years. These devices can be devices such as computers, tabletcomputers, televisions, multimedia devices, mobile devices, and thelike.

In some circumstances, system controls or notifications are accessiblethrough user interfaces on such a device, and user interaction with sucha device entails accessing such user interfaces. Enhancing theseinteractions improves the user's experience with the device anddecreases user interaction time, which is particularly important whereinput devices are battery-operated.

SUMMARY OF THE DISCLOSURE

Some embodiments described in this disclosure are directed to one ormore electronic devices that provide access to a system user interface(e.g., for controlling device functions and/or viewing or interactingwith notifications) in response to touch inputs received in anapplication user interface or a wake screen user interface, and one ormore operations related to the above that the electronic devicesoptionally perform. The full descriptions of the embodiments areprovided in the Drawings and the Detailed Description, and it isunderstood that the Summary provided above does not limit the scope ofthe disclosure in any way.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6XX illustrate exemplary ways in which an electronic deviceprovides access to a system user interface in response to touch inputsreceived in an application user interface or a wake screen userinterface, in accordance with some embodiments of the disclosure.

FIGS. 7A-7H are flow diagrams illustrating a method of providing accessto a system user interface in response to touch inputs received in anapplication user interface or a wake screen user interface, inaccordance with some embodiments of the disclosure.

DETAILED DESCRIPTION Description of Embodiments

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for accessing a system user interface (e.g., forcontrolling device functions and/or viewing or interacting withnotifications) in response to touch inputs received in an applicationuser interface or a wake screen user interface. Such techniques canreduce the amount of time needed by a user to perform operations,thereby enhancing productivity and reducing the power usage of thedevice and increasing battery life for battery-powered devices.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 700 (FIG.7). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

User Interfaces and Associated Processes Accessing System UserInterfaces from Application or Wake Screen User Interfaces

Users interact with electronic devices in many different manners,including interacting with wake screen user interfaces of the devices(e.g., the first user interface displayed on the devices when thedevices exit from a sleep or idle state, such as a watch face userinterface on a smart watch) and application user interfaces forapplications that may be available on the electronic devices. Forexample, a user provides various types of touch inputs to applicationuser interfaces displayed on a display of an electronic device. However,in some circumstances, the user wishes to quickly and expedientlycontrol various system functions and/or access various system andapplication notifications using various touch inputs, but cannot do sowithout first exiting a displayed application user interface andnavigating to a different user interface from which such controls and/ornotifications are accessible. The embodiments described below provideways in which an electronic device provides access to a system userinterface (e.g., for controlling device functions and/or viewing orinteracting with notifications) in response to touch inputs received inan application user interface or a wake screen user interface, therebyenhancing the user's interactions with the electronic device. Enhancinginteractions with a device reduces the amount of time needed by a userto perform operations, and thus reduces the power usage of the deviceand increases battery life for battery-powered devices. It is understoodthat people use devices. When a person uses a device, that person isoptionally referred to as a user of the device.

FIGS. 6A-6XX illustrate exemplary ways in which an electronic deviceprovides access to a system user interface in response to touch inputsreceived in an application user interface or a wake screen userinterface, in accordance with some embodiments of the disclosure. Theembodiments in these figures are used to illustrate the processesdescribed below, including the processes described with reference toFIGS. 7A-7H.

FIGS. 6A-6C illustrate various embodiments where a swipe input isdetected on the touch screen of an electronic device while the touchscreen displays an application user interface.

FIG. 6A illustrates exemplary device 600 with touch screen 604, such asdescribed with reference to FIGS. 5A-5H. Touch screen 604 optionallydisplays one or more user interfaces that include various content. Inthe example illustrated in FIG. 6A, touch screen 604 displays a fitnesstracking application user interface 602 of a fitness trackingapplication for tracking various data related to workout sessions of auser. In FIG. 6A, the fitness tracking application displays workout typebrowsing user interface 602, which includes multiple affordancesassociated with different workout sessions. For example, the “IndoorWalk” affordance 608 is associated with functions used in an indoor walkworkout session, while affordances “Outdoor Cycle” and “Outdoor Run” areassociated with functions used in an outdoor cycle and an outdoor runworkout session, respectively. In another example, affordance “QuickStart” is associated with a frequently-selected exercise session or themost recent exercise session (in this case, a strength training exercisesession). The affordances optionally further display information relatedto the type of workout session such as the date and the distance of thelast outdoor run in the outdoor run affordance. Touch screen 604 furtherincludes a top region 616, whose top boundary is the top edge of thetouch screen 604 and whose bottom boundary is the first dashed line fromthe top edge of the touch screen 604 in FIG. 6A. Similarly, touch screen604 further includes a bottom region 618, whose top boundary is thefirst dashed line from the bottom edge of the touch screen 604 and whosebottom boundary is the bottom edge of touch screen 604 in FIG. 6A. Asshown in FIG. 6A, top region 616 is larger than bottom region 618.Further, part of the quick start affordance is in the top region 616,and part of the indoor walk affordance 608 is in the bottom region 618.Time bar 610 depicts the time duration of a touch input detected at thetouch screen 604 (e.g., reflecting the elapsed time since the time whena contact in the touch input is first detected on touch screen 604), andtime threshold 612 depicts a predefined minimum time threshold a touchinput must meet in order to satisfy a requirement to display anindication of the above-mentioned system user interface that isoptionally accessible from user interface 602, as will be described inmore detail later. Furthermore, contact 606 is detected at an area ofthe touch screen where indoor walk affordance 608 is being displayed;that is, contact 606 overlaps with indoor walk affordance 608. Becausecontact 606 has just been detected at the touch screen 604 in FIG. 6A,time bar 610 shows no elapsed time since touchdown of contact 606 ontouch screen 604.

In FIG. 6B, as the contact time elapses (as shown in the solid portionof the contact bar 610), but before the elapsed contact time reaches apredefined minimum time threshold 612, an upward movement of contact 606is detected on touch screen 604. Generally, a vertical (e.g., upward ordownward) movement is considered a swipe or flick input (e.g., a swipewhere the movement speed is relatively slow and the movement distance isrelatively long, or a flick where the movement speed is relatively fastand the movement distance is relatively short). A swipe (or flick)detected in an application user interface will optionally result in ascrolling behavior through that user interface in accordance with theswipe (or flick). For example, FIG. 6B depicts the upward movement ofcontact 606 out of the bottom region 618 while the touch screen 604displays the workout type browsing user interface 602. In response, theworkout type browsing user interface 602 displays additional affordances(e.g., Elliptical and Rower affordances) near the bottom of the touchscreen 604, shifts some already displayed affordances upward, and stopsdisplaying affordances previously near the top of the touch screen 604(e.g., the Quick Start affordance). Optionally, a scrolling behavior inthe application user interface is also achieved by receiving a non-touchinput, such as a rotation input at a digital crown of a smart watchdevice.

In FIG. 6C, the elapsed time in time bar 610 is reset to null, signalingthat the upward swipe input has completed (e.g., a liftoff of contact606 was detected after detecting the swipe input). In response todetecting the swipe input, the workout type browsing user interface 602optionally displays additional affordances (e.g., the partially visibleStair Master affordance) near the bottom of the touch screen 604, shiftssome already displayed affordances upward, and stops displayingaffordances previously near the top of the touch screen 604 (e.g., theOutdoor Run affordance). Thus, as described with reference to FIGS.6A-6C, a swipe input (e.g., vertical swipe input) detected in anapplication user interface optionally results in scrolling through thatapplication user interface in accordance with the swipe input.

Similarly, a tap input detected in an application user interfaceoptionally results in the application user interface responding to thetap input. For example, FIGS. 6D-6E illustrate various embodiments wherea tap input is detected on the touch screen of an electronic devicewhile the touch screen displays an application user interface.

In FIG. 6D, touch screen 604 is displaying fitness tracking applicationuser interface 602 as discussed above while contact 606, which overlapswith the boundary of the Indoor Walk affordance 608, is received in thebottom region 618. As seen on time bar 610, contact 606 has not beendetected long enough to reach the time threshold 612, which again is thepredefined minimum time threshold a touch input must meet in order tosatisfy a requirement (e.g., in order to be considered a touch and holdinput) to display an indication of the above-mentioned system userinterface that is optionally accessible from user interface 602, as willbe described in more detail later. Furthermore, contact 606 is detectedat an area of the touch screen where indoor walk affordance 608 is beingdisplayed; that is, contact 606 overlaps with indoor walk affordance608. Contact time begins to elapse as shown in time bar 610.

In FIG. 6E, the elapsed time in time bar 610 is reset to null, signalinga liftoff of contact 606 was detected before contact 606's durationreached the time threshold 612. As a result, contact 606 is optionallyconsidered to be part of a tap input. In response to detecting the tapinput, an Indoor Walk exercise user interface 602 (corresponding to theselected indoor walk affordance 608) is optionally displayed, as shownin FIG. 6E. The Indoor Walk exercise user interface 602 in FIG. 6Eincludes additional affordances (e.g., a Start affordance to start theindoor walk exercise session and two affordances with a “+” sign and a“−” sign, respectively, for adjusting the desired distance of the indoorwalk exercise session) and status indicators (e.g., the current timeindicator on the top right corner of touch screen 604).

As previously mentioned, in some embodiments, actions other than swipingthrough an application user interface or having the application userinterface respond to a touch input to display another application userinterface are achievable from the application user interface. FIGS.6F-6K illustrate various embodiments where a touch and hold inputfollowed by a swipe input is detected on the touch screen of anelectronic device while the touch screen displays an application userinterface, and rather than interacting with the application userinterface, the touch and hold input provides for access to a system userinterface of the electronic device (e.g., a user interface that is not auser interface of the application, but rather a user interface of theoperating system of the electronic device).

In FIG. 6F, touch screen 604 is displaying fitness tracking applicationuser interface 602 discussed in detail above. As shown in the figure,part of the quick start affordance is in the top region 616, and part ofthe indoor walk affordance 608 is in the bottom region 618. Because nocontact is detected at the touch screen, time bar 610 shows no elapsedtime duration.

FIG. 6G depicts the moment that a contact 606 is detected in the bottomregion 618 of touch screen 604 while the touch screen 604 displays theworkout type browsing user interface 602. Furthermore, the contact 606is detected in an area of the touch screen where indoor walk affordance608 is being displayed; that is, contact 606 overlaps with indoor walkaffordance 608. Contact time begins to elapse.

In FIG. 6H, contact 606 continues to be detected (e.g., without liftoff)in bottom region 618 and overlaps with indoor walk affordance 608. Timebar 610 shows that some time has elapsed (shown in solid), but theelapsed time has not exceeded the predefined time threshold 612.

In FIG. 6I, the elapsed time (shown in solid in time bar 610) hasreached the predefined time threshold 612 while contact continuedContact 606 to be detected (e. g., there was no liftoff) in bottomregion 618 contact 606. As a result, contact 606 is optionallyconsidered to be part of a touch and hold input. In response todetermining that contact 606 is part of a touch and hold input, touchscreen 604 displays system user interface indication 611 and optionallya partial view of system user interface 614 (e.g., partial views ofaffordances in system user interface 614) in proximity to contact 606(e.g., peeking up from the bottom portion of touch screen 604,corresponding to the bottom region 618 of touch screen 604 in whichcontact 606 was detected). Additionally, system user interfaceindication 611 and the partial view of system user interface 614partially obscure workout type browsing user interface 602, whose sizehas been reduced proportionally (e.g., while maintaining its originalaspect ratio) and has been pushed back on touch screen 604 to appear asif it is behind system user interface 614. Furthermore, electronicdevice 600 optionally provides a tactile output (e.g., a vibration)and/or an audio response such as a beep when the touch and hold input isdetected. The combination of displaying system user interface indication611, obscuring workout type browsing user interface 602, pushing workouttype browsing user interface 602 back on touch screen 604 and providingtactile/audio response optionally indicates to the user that a systemuser interface (e.g., system user interface 614) is accessible upondetection of further input.

In FIG. 6J, an upward movement of contact 606 is detected withoutliftoff of contact 606 being detected. This upward movement isconsidered a further touch input (e.g., a swipe input or a flick input)on touch screen 604. Time bar 610 with a larger solid stripe shows thatbefore detecting the swipe input, the contact 606 continues to bedetected on touch screen 604 (e.g., there is no liftoff between thetouch and hold input and the swipe input). In response to detecting thata swipe of contact 606 has commenced, touch screen 604 displays a largerpartial view of system user interface 614 (e.g., partial views of otheraffordances in system user interface 614) relative to that in FIG. 6D asif the swipe of contact 606 upward is pulling system user interface 614into touch screen 604, and further obscures workout type browsing userinterface 602. Touch screen 604 optionally ceases to display system userinterface indicator 611 at this point.

In FIG. 6K, the upward swipe or flick input has completed. System userinterface 614, whose partial view was optionally shown in FIG. 6J, isfully displayed on touch screen 604 in FIG. 6K (e.g., has been fullypulled into view on touch screen 604 by the swipe input). System userinterface 614 in FIG. 6K includes affordances that allow a user to viewand change the statuses of system functions of the electronic device600, such as viewing the Wi-Fi status and turning the Wi-Fi radio on andoff via a Wi-Fi status affordance. Thus, as described above, a user itable to access a system user interface from an application userinterface in response to a touch and hold input detected in the bottomregion of the touch screen, followed by an upward swipe input that pullsthe system user interface into view on the touch screen.

The system user interface is optionally similarly accessible from a wakescreen user interface (e.g., a watch face) of the electronic device 600.FIGS. 6L-6N illustrate various embodiments where a touch and hold inputfollowed by a swipe input is detected on the touch screen of anelectronic device while the touch screen displays a wake screen userinterface.

In the example illustrated in FIG. 6L, touch screen 604 displays adevice wake screen (e.g., a watch face in the case that the electronicdevice is a smart watch) user interface 603 for displaying variousinformation and providing access to various watch functions and/orinstalled applications. In FIG. 6L, the wake screen user interface 603includes a simulated analog watch face and multiple affordancesassociated with different functions and/or applications. For example,the affordance 617 is selectable to activate a stopwatch or chronographfunction of the electronic device. In another example, the affordance atthe top left corner of the wake screen user interface 603 is selectableto control connected smart appliances. In another example, theaffordance at the top right corner of wake screen user interface 603 isselectable to control playback of media files (e.g., music). Similar topreviously discussed exemplary embodiments, touch screen 604 includes atop region 616 and a bottom region 618, where top region 616 is largerthan bottom region 618. The smart home function affordance and themedia-playing application affordance both are in the top region 616,while the stopwatch affordance 617 is in the bottom region 618. In FIG.6L, contact 606 has just been detected in the bottom region 618 of touchscreen 604 while the touch screen 604 displays the wake screen userinterface 603; thus, time bar 610 shows no elapsed time duration, butcontact time has begun to elapse.

In FIG. 6M, the elapsed time (shown in solid in time bar 610) hasreached the predefined time threshold 612 while contact 606 has remainedin the bottom region 618 of touch screen 604. contact 606 Just asdescribed with reference to FIG. 6I, in response to determining thatcontact 606 is part of a touch and hold input, touch screen 604 displayssystem user interface indication 611 and optionally a partial view ofsystem user interface 614 that obscures wake screen user interface 603.Furthermore, electronic device 600 optionally provides a tactile output(e.g., a vibration) and/or an audio response such as a beep. Otherdetails of the response of device 600 to the touch and hold inputdetected in bottom region 618 of touch screen 604 are optionally thesame as described with reference to FIGS. 6F-6K.

For example, in FIG. 6N, a further upward swipe or flick of contact 606is detected and completed, similar to the embodiment discussed in FIG.6K. System user interface 614 (similar to that in FIG. 6K), whosepartial view was optionally shown in FIG. 6M, is displayed on touchscreen 604 in FIG. 6N.

FIGS. 6O-6R illustrate various embodiments where a touch and hold inputfollowed by a liftoff of contact 606 is detected on the touch screen ofan electronic device while the touch screen displays a wake screen userinterface.

In FIG. 6O, device 600 is displaying wake screen user interface 603,similar to that in FIG. 6L. Contact 606 has just been detected in thebottom region 618 of touch screen 604 while touch screen 604 displaysthe wake screen user interface 603; thus, time bar 610 shows no elapsedtime duration, but contact time has begun to elapse.

In FIG. 6P, as in FIG. 6M, the elapsed time (shown in solid in time bar610) of contact 606 has reached the predefined time threshold 612, anddevice 600 responds as described in FIG. 6I or 6M, for example.

In FIG. 6Q, a liftoff of contact 606, instead of a swipe of contact 606,is detected on touch screen 604 while system user interface indication611 is being displayed in response to detecting the touch and hold inputin FIG. 6P. In response to detecting the liftoff, touch screen 604ceases to display system user interface indication 611 and the partialview of system user interface indication 614 and resumes displaying wakescreen user interface 603, as shown in FIG. 6R. For example, system userinterface indication 611 disappears, the partial view of system userinterface indication 614 begins to recede down and out of view towardsthe bottom edge of touch screen 604, while the obscured and reduced-sizewake screen user interface 603 begins to return to the foreground and toits original size in FIG. 6O, as shown in FIG. 6R.

In FIG. 6R, the electronic device 600 returns to the same state as inFIG. 6O, that is, before detecting a touch input contact on touch screen604. For example, system user interface indication 611 has receded outof view through the bottom edge of touch screen 604, while thepreviously obscured and reduced-size wake screen user interface 603 hasreturned to the foreground and its original size. Further, in FIG. 6R,affordance 617 has not been activated by the sequence of events ofcontact 606 described in FIGS. 6O-6Q (e.g., liftoff of contact 606 afterreaching time threshold 612 without detecting a swipe of contact 606does not interact with the user interface, and merely causes the systemuser interface indications to cease being displayed and the userinterface to be redisplayed in its full, unobscured state).

The same result as described with reference to FIGS. 6O-6R optionallyoccurs when device 600 is displaying an application user interface asopposed to a wake screen user interface. For example, in FIGS. 6S-6V, atouch and hold of contact 606 is detected in bottom region 618 of touchscreen 604 while the fitness application user interface is beingdisplayed, liftoff of contact 606 in bottom region 618 is detected, andas a result the fitness application user interface is redisplayed infull on touch screen 604 without indoor walk affordance 608 having beenactivated by contact 606.

FIGS. 6W-6X illustrate various embodiments where a tap input instead ofa touch and hold input is detected in the bottom region of the touchscreen of an electronic device while the touch screen displays a wakescreen user interface.

In FIG. 6W, touch screen 604 is displaying wake screen user interface603, as previously described, when contact 606, which overlaps withstopwatch affordance 617, is detected in the bottom region 618 of touchscreen. As seen on time bar 610, contact 606 has not been detected longenough to reach the time threshold 612.

Before time threshold 612 is reached, liftoff of contact 606 isdetected, and as a result contact 606 is optionally determined to bepart of a tap input. In response to detecting the tap input on stopwatchaffordance 617, device 600 displays a stop watch user interface 605 asshown in FIG. 6X. The stopwatch user interface 605 in FIG. 6X includesadditional affordances (e.g., a Lap affordance to record a lap time anda stop affordance to stop recording elapsed time in the stopwatchapplication) and status indicators (e.g., the current time indicator onthe top right corner of touch screen 604). A tap input detected on anaffordance in an application user interface within bottom region 618 ortop region 616 optionally similarly results in activation of theaffordance, and causes device 600 to respond accordingly.

In some embodiments, the system user interface is accessible from a wakescreen user interface in response to a swipe input without a requiredtouch and hold input, in contrast to the behavior of device 600 whendisplaying an application user interface. FIGS. 6Y-6AA illustratevarious embodiments where a swipe input instead of a touch and holdinput is detected on the touch screen of an electronic device while thetouch screen displays a wake screen user interface.

In FIG. 6Y, touch screen 604 is displaying a wake screen user interface603 (e.g., a watch face in the case that the electronic device is asmart watch), as previously described. Contact 606 has just beendetected in bottom region 618 of touch screen 604.

In FIGS. 6Z to 6AA, before the elapsed contact time reaches timethreshold 612, an upward swipe of contact 606 is detected on touchscreen 604. As mentioned previously, a swipe (or flick) detected in awake screen user interface will optionally result in the display of asystem user interface, sometimes without displaying first an indicationof that system user interface. For example, in response to detecting theupward swipe of contact 606, touch screen 604 optionally displays apartial view of system user interface 614, and as the swipe continues topull system user interface 614 into view, eventually the entirety ofsystem user interface 614 is displayed on touch screen, as in FIG. 6AA.Thus, as described with reference to FIGS. 6Y to 6AA, system userinterface 614 is optionally accessible from a wake screen user interfacein response to a swipe input without an intervening touch and holdinput.

In some embodiments, the system user interface is accessible via a touchand hold input that occurs off of, but near, the touch screen. FIGS.6BB-6EE illustrate various embodiments where a touch screen detects anobject near the edge of the touch screen, but not on the touch screen,followed by a subsequent swipe input detected on the touch screen whilethe touch screen displays an application user interface.

In FIG. 6BB, as in FIG. 6S, touch screen 604 is displaying fitnesstracking application user interface 602 discussed in detail above.Specifically, touch screen 604 detects an object 609 (e.g., a user'sfinger) near the bottom edge of bottom region 618 (of touch screen 604)but not on the touch screen 604. In some embodiments, object 609 isanalogously detected near the top edge of top region 616 (of touchscreen 604), and device 600 will optionally respond analogously to asdescribed with reference to FIGS. 6TT-6VV. In FIG. 6BB, object 609 hasjust been detected near the bottom edge of bottom region 616, asindicated by time bar 610.

In FIG. 6CC, the elapsed time (shown in solid in time bar 610) hasreached the time threshold 612 while object 609 continues to be detectednear the bottom edge of bottom region 618 (e.g., there was no liftoff ofobject 609). In response to determining that object has been detectednear the bottom edge of bottom region 618, touch screen 604 displayssystem user interface indication 611 and optionally a partial view ofsystem user interface 614 (e.g., partial views of other affordances insystem user interface 614) in proximity to detected object 609.Additionally, system user interface indication 611 and the partial viewof system user interface 614 partially obscure workout type browsinguser interface 602, whose size has reduced proportionally (e.g., whilemaintaining its original aspect ratio) and has been pushed back on touchscreen 604 to appear as if it is behind system user interface 614.Furthermore, electronic device 600 optionally provides a tactile output(e.g., a vibration) and/or an audio response such as a beep. Otherdetails of the response of device 600 to the touch and hold inputdetected near, but not in bottom region 618 of touch screen 604, areoptionally the same as described with reference to FIGS. 6G-6I.

In FIG. 6DD, an upward movement of contact 606 is detected withoutliftoff of object 609 being detected, indicating that an upward swipeinput is detected on touch screen 604 (e.g., object 609 has moved fromthe bottom edge of device 600 onto touch screen 604 as it swipes upwardacross touch screen 604). This upward movement is optionally considereda further touch input (e.g., a swipe input or a flick input) on touchscreen 604, like in FIGS. 6J-6K. In response to detecting that a furtherswipe input has commenced, touch screen 604 optionally displays a largerpartial view of the system user interface 614, as shown in FIG. 6DD, andas the swipe continues to pull system user interface 614 into view,eventually the entirety of system user interface 614 is displayed ontouch screen as if the swipe of contact 606 upward is pulling systemuser interface 614 into touch screen 604, as shown in FIG. 6EE. Touchscreen 604 optionally ceases to display system user interface indicator611 at this point.

In some embodiments, after the electronic device receives a touch andhold input in an application user interface or a wake screen userinterface, inputs other than swiping optionally allow for access to thesystem user interface as well. For example, FIGS. 6FF-6JJ illustratevarious embodiments where the same result as described with reference toFIGS. 6F-6K optionally occurs when device 600 is displaying anapplication user interface and when a touch and hold input followed by ahard press input are detected on the touch screen of an electronicdevice.

For example, in FIG. 6FF, touch screen 604 is displaying fitnesstracking application user interface 602 as discussed above. Contact 606,which overlaps with the boundary of the Indoor Walk affordance 608, isdetected in the bottom region 618 of touch screen 604. Notably,intensity bar 620 depicts the intensity (e.g., the downward pressureagainst the touch sensitive surface of touch screen 604) of contact 606,and intensity threshold 622 depicts a predefined intensity threshold acontact must reach in order to eventually cause display of the systemuser interface 614, as will be described below. As seen on time bar 610in FIG. 6FF, contact time has begun to elapse, but contact 606 has notbeen detected long enough to reach the time threshold 612. Furthermore,as seen on intensity bar 620, contact 606 has not reached the intensitythreshold 622.

In FIG. 6GG, the elapsed time (shown in solid in time bar 610) ofcontact 606 has reached the predefined time threshold 612 while theintensity of contact 606 has not yet reached intensity threshold 622. Asa result, contact 606 is optionally considered to be part of a touch andhold input. In response to determining that contact 606 is considered tobe part of a touch and hold input, device 600 responds as described inFIG. 6I, for example (e.g., displays a portion of system user interface614, generates a tactile output, etc., as shown in FIG. 6GG).

In FIG. 6HH, after contact 606 has met the time threshold 612 (asdepicted in the solid portion of time bar 610), the intensity of contact606 increases, as depicted in the solid portion of intensity bar 620.Touch screen 604 continues to display system user interface indication611 and the partial view of system user interface 614 as in FIG. 6GGwithout further tactile output or audio response.

In FIG. 6II, as contact 606 continues, the intensity of touch input 606has reached the intensity threshold 622, as depicted in the solidportion of intensity bar 620. As a result, contact 606 is considered tobe part of a further touch input (e.g., a hard press input) on touchscreen 604. In response to detecting the further hard press input,device 600 generates a tactile output corresponding to the intensity ofcontact 606 reaching intensity threshold 622, and displays on touchscreen 604 a larger partial view of system user interface indication 614(e.g., partial views of other affordances in system user interface 614)relative to that in FIG. 6HH as if the system user interface 614 isbeing pushed or pulled into touch screen 604 by the increased intensityof contact 606, and further obscures workout type browsing userinterface 602, eventually displaying fully system user interface 614, asshown in FIG. 6JJ. Touch screen 604 optionally ceases to display systemuser interface indicator 611 at this point. Thus, system user interface614 is displayed on touch screen 604 without detecting a swipe ofcontact 606 on touch screen 604.

In some embodiments, the system user interface is accessible via a hardpress input without first requiring a push and hold input in anapplication user interface or a wake screen user interface. For example,FIGS. 6KK and 6MM illustrate various embodiments where a hard pressinput is detected in the top or bottom regions of the touch screen of anelectronic device while the touch screen displays an application userinterface.

In FIG. 6KK, touch screen 604 is displaying fitness tracking applicationuser interface 602, as discussed above, when contact 606, which overlapswith the boundary of the Indoor Walk affordance 608, is detected in thebottom region 618 of touch screen 604. Intensity bar 620 depicts thatthe intensity of contact 606 has not reached a predefined intensitythreshold 622. Similarly, time bar 610 depicts that contact time hasbegun to elapse but has not been detected long enough to reach the timethreshold 612.

In FIG. 6LL, the intensity of contact 606 has reached the intensitythreshold 622 before the contact time has reached the time threshold612. As a result, contact 606 is considered to be part of a hard pressinput. In response to determining that a hard press input is detected inthe bottom region 618 of touch screen 604, the electronic deviceoptionally generates a tactile output corresponding to the intensity ofthe contact reaching the intensity threshold 622, and displays systemuser interface 614 similar to as in FIGS. 6II and 6JJ, sometimes withoutfirst displaying an indication of that system user interface (e.g.,indication 611). For example, in response to determining that contact606 is part of a hard press input, touch screen 604 optionally displaysa partial view of system user interface 614 that appears as if beingpushed or pulled into touch screen 604, eventually displaying fullysystem user interface 614, as shown in FIG. 6MM. Thus, system userinterface 614 is displayed on touch screen 604 without first detecting atouch and hold input, and without detecting a swipe of contact 606 ontouch screen 604.

In some embodiments, the system user interfaces of the disclosure arenot accessible via a hard press input in an application user interfaceor a wake screen user interface if the hard press input is detectedoutside of certain regions of the touch screen. For example, FIGS. 6NNand 6OO illustrate various embodiments where a hard press input isdetected near the center of the touch screen (e.g., outside of the topand bottom regions of the touch screen) of an electronic device whilethe touch screen displays an application user interface.

In FIG. 6NN, touch screen 604 is displaying fitness tracking applicationuser interface 602 as discussed above while contact 606, which overlapswith the boundary of the Outdoor Cycle affordance 608, is detectedoutside of both the top region 616 and the bottom region 618 of touchscreen 604. Intensity bar 620 depicts that the intensity of contact 606has not reached a predefined intensity threshold 622. Similarly, timebar 610 depicts that contact time has begun to elapse but has not beendetected long enough to reach the time threshold 612.

In FIG. 6OO, before time threshold 612 is reached, the intensity ofcontact 606 has reached the intensity threshold 622. As a result,contact 606 is considered to be part of a hard press input. In responseto determining that a hard press input is detected outside of both thetop region 616 and the bottom region 618 of touch screen 604, touchscreen 604 does not display a system user interface. Instead, forexample, in response to detecting the hard press input contact 606 infitness tracking application user interface 602, touch screen 604optionally displays fitness tracking application user interface 602where the size of interface 602 slightly reduces proportionally andimmediately returns to its original size, thus creating a “shrink andbounce back” visual effect, because no action is accessible via a hardpress input detected in this user interface of the fitness trackingapplication. More generally, a hard press input detected outside of thetop and bottom regions of touch screen 604 while touch screen 604 isdisplaying an application user interface optionally results in an inputprovided to the application in accordance with the hard press input(e.g., as opposed to providing access to the system user interfaces ofthe disclosure).

In another example, FIGS. 6PP and 6QQ illustrate various embodimentswhere a hard press input is detected near the center of the touch screen(e.g., outside of the top and bottom regions of the touch screen) of anelectronic device while the touch screen displays a wake screen userinterface.

In FIG. 6PP, touch screen 604 is displaying a device wake screen userinterface 602 when contact 606 is detected outside of both the topregion 616 and the bottom region 618 of touch screen 604. Intensity bar620 depicts that the intensity of contact 606 has not reached apredefined intensity threshold 622. Similarly, time bar 610 depicts thatcontact time has begun to elapse but has not been detected long enoughto reach the time threshold 612.

In FIG. 6QQ, before time threshold 612 is reached, the intensity ofcontact 606 has reached the intensity threshold 622. As a result,contact 606 is considered to be part of a hard press input. In responseto determining that a hard press input is detected outside of both thetop region 616 and the bottom region 618 of touch screen 604, touchscreen 604 does not display a system user interface. Instead, touchscreen 604 optionally displays in the center of the display arepresentation of wake screen user interface 603 at a proportionallyreduced size (e.g., while maintaining its original aspect ratio) and oneach side a partial view of a representation of another wake screen userinterface (e.g., other watch faces accessible on device 600) at aproportionally reduced size. The user is optionally able to providehorizontal (leftward or rightward) swipe inputs to scroll through thereduced-size representations of various wake screen user interfaces(e.g., watch faces). The touch screen 604 optionally displays a“Customize” affordance that is selectable to access functions thatcustomize the wake screen user interface. More generally, a hard pressinput detected outside of the top and bottom regions of touch screen 604while touch screen 604 is displaying a wake screen user interfaceoptionally results in an input provided to the wake screen userinterface in accordance with the hard press input (e.g., providingaccess to a watch face editing user interface as opposed to providingaccess to the system user interfaces of the disclosure).

In some embodiments, after displaying the system user interface, theelectronic device optionally allows for reconfiguration of theaffordances in the system user interface in response to further touchinput, as illustrated in FIGS. 6RR and 6SS.

In FIG. 6RR, touch screen 604 is displaying system user interface 614 asdescribed previously in, for example, FIG. 6K. While displaying systemuser interface 614, contact 606, which overlaps with an affordance insystem user interface 614 (e.g., the Theater Mode affordance), isdetected on touch screen 604. Time bar 630 depicts the time duration ofcontact 606, and time threshold 632 depicts a predefined minimum timethreshold that a contact overlapping with a system affordance in systemuser interface 614 must meet in order to operate system user interface614 in a reconfiguration mode (e.g., a mode in which a tap and draginput on an affordance in the system user interface 614 will move theaffordance to a new position in the system user interface 614 inaccordance with the drag). In some embodiments, time threshold 632 isthe same as time threshold 612 described previously, and in someembodiments, time threshold 632 is different than time threshold 612described previously.

In FIG. 6SS, contact 606 has been detected on touch screen 604 for timethreshold 632. In response, system user interface 614 in FIG. 6SS nowoperates in a reconfiguration mode in which the selectable affordancesare repositionable using various types of touch inputs (e.g., tap anddrag inputs on the affordances). In some embodiments, thereconfiguration mode is indicated by one or more visual indications. Forexample, in one embodiment, the selectable system affordances jiggle asthough they are floating on water (e.g., each respective selectablesystem affordance oscillates about a respective average position of theselectable system affordance on the display).

In some embodiments, touch inputs (e.g., touch and hold inputs;off-screen touch and hold; etc., as previously described) received inthe top region of a touch screen while displaying an application userinterface or a wake screen user interface optionally provide access toanother system user interface, different from the one accessible throughtouch inputs (e.g., touch and hold inputs; off-screen touch and hold;etc., as previously described) received in the bottom region of thetouch screen. However, access to the other system user interface fromthe top region of the touch screen is optionally analogous and includesthe same features as those described with reference to FIGS. 6A-6MM. Insome embodiments, the system user interface accessible from the bottomregion of the touch screen is a user interface for controlling one ormore functions of the electronic device (e.g., a control center), andthe system user interface accessible from the top region of the touchscreen is a user interface for viewing one or more notificationsgenerated at the electronic device (e.g., a notification center). Forexample, FIGS. 6TT and 6VV illustrate exemplary embodiments where anelectronic device provides access to a notification center userinterface in response to detecting a touch and hold input in the topregion of a touch screen and then a downward swipe input.

In FIG. 6TT, touch screen 604 is displaying fitness tracking applicationuser interface 602 discussed in detail above, while contact 606 isbeginning to be detected in the top region 616 of touch screen 604, andcontact 606 overlaps with Quick Start affordance 625.

In FIG. 6UU, the elapsed time (shown in solid in time bar 610) hasreached the predefined time threshold 612. As a result, contact 606 isconsidered to be part of a touch and hold input. In response todetermining that contact 606 is a touch and hold input, touch screen 604displays in proximity to contact 606, system user interface indication613 and optionally a partial view of system user interface 615, whichdisplays notifications associated with the system and/or withapplications installed on the electronic device. Electronic device 600optionally obscures/pushes back workout type browsing user interface 602and provides a tactile output and/or an audio response similar topreviously discussed embodiments.

In FIG. 6VV, a downward swipe or flick of contact 606 is detected andcompleted after the touch and hold input, analogous to the upward swipesor flicks described with reference to previous embodiments. In responseto detecting the further downward swipe input across touch screen 604,device 600 fully displays system user interface 615, as shown in FIG.6VV. Touch screen 604 optionally ceases to display system user interfaceindicator 613 at this point. Thus, as described above, a control centeruser interface or a notification center of the electronic device areaccessible from an application user interface or a wake screen userinterface from the bottom or top regions, respectively, of the touchscreen as described with reference to FIGS. 6F-6VV.

The various embodiments described above are optionally operable in botha left-handed configuration and a right-handed configuration. Forexample, device 600 is optionally a smart watch that is wearable on auser's left wrist or a user's right wrist. Further, the top region ofthe touch screen is optionally larger than the bottom region of thetouch screen, as previously described. However, the physical portion ofthe touch screen that corresponding to the top region (and the bottomregion) will optionally be different depending on whether device 600 isworn on the user's left wrist or the user's right wrist. Thus, in orderto ensure that the region of the touch screen that is larger is theregion of the touch screen that is on top regardless of whether the userraises their left wrist to look at device 600 (if device 600 is beingworn on the left wrist) or the user raises their right wrist to look atdevice (if device 600 is being worn on the right wrist), device 600optionally selects the top and bottom regions of the touch screen to bedifferent physical portions of the touch screen depending on whetherdevice 600 is in a left-handed configuration (e.g., configured to beworn on a user's right wrist) or a right-handed configuration (e.g.,configured to be worn on a user's left wrist). For example, FIGS. 6WWand 6XX illustrate exemplary embodiments where device 600, a wrist-wornsmart watch, is operated in a left-handed (worn on the right wrist) anda right handed (worn on the left wrist) configuration, respectively.

In FIG. 6WW, device 600 is a smart watch with an asymmetrically-locatedcrown operating in a left-handed configuration (e.g., on the user'sright wrist). Top region 616 is in the top portion of the touch screenwhen the user raises their right wrist to view the screen, and bottomregion 618 is in the bottom portion of the screen when the user raisestheir right wrist to view the screen (e.g., top region 616 is locatedfarther from the crown, and bottom region 618 is located closer to thecrown).

In FIG. 6XX, device 600 is the smart watch with theasymmetrically-located crown described in FIG. 6WW, but operating in aright-handed configuration (e.g., on the user's left wrist). Top region616 is in the top portion of the touch screen when the user raises theirleft wrist to view the screen, and bottom region 618 is in the bottomportion of the screen when the user raises their left wrist to view thescreen (e.g., top region 616 is located closer to the crown, and bottomregion 618 is located farther from the crown). In this way, device 600is able to change its top/bottom configurations depending on which wristof the user device 600 is on to maintain consistency of the relativesizes of the top and bottom regions of the touch screen.

FIGS. 7A-7H are flow diagrams illustrating a method 700 of providingaccess to a system user interface in response to touch inputs receivedin an application user interface or a wake screen user interface inaccordance with some embodiments of the disclosure. The method 700 isoptionally performed at an electronic device such as device 100, device300 or device 500 as described above with reference to FIGS. 1A-1B, 2-3,4A-4B and 5A-5H. Some operations in method 700 are, optionally, combinedand/or the order of some operations is, optionally, changed.

In some embodiments, such as in FIG. 6G, an electronic device (e.g., apersonal wearable device such as a smart watch, a mobile device such asa mobile phone, or a TV set-top box, such as device 600) incommunication with a display (e.g., a watch display, a smartphonedisplay, or a television set, such as touch screen 604) and atouch-sensitive surface (e.g., a touch screen of a smartphone, a touchscreen of a smart watch, or a touch-sensitive surface of a remotecontrol of a set-top box, such as touch screen 604) displays (702), onthe display, a user interface (e.g., a system user interface of theelectronic device such as a wake screen of a smart watch (e.g., a watchface or other user interface that is the first user interface displayedby the electronic device when it wakes from a sleep state such as inFIG. 6L), or an application user interface of one or more applicationsinstalled on the electronic device (e.g., the user interface of afitness tracking application running on the electronic device such as inFIG. 6A). In some embodiments, the wake screen is a watch face andincludes one or more watch complications such as time and date, and/orone or more affordances corresponding to applications installed on thewatch or features of the watch such as in FIG. 6L (e.g., an affordanceselectable to launch an installed instant messaging application, anaffordance selectable to launch a fitness tracking application, etc.).In some embodiments, the user interface is an application userinterface, such as a user interface of a fitness tracking applicationdisplaying one or more indicators (e.g., the user's heart rate andelapsed time of exercise) or affordances (e.g., affordances to start,pause or stop an exercise)).

In some embodiments, such as in FIG. 6G, while displaying the userinterface on the display, the electronic device (600) receives (704) atouch input comprising a contact detected on the touch-sensitive surface(e.g., detecting a contact (e.g., 606) on a touch screen display (e.g.,604) of the smart watch. In some embodiments, the contact is from afinger of the user).

In some embodiments, in response to receiving the touch input,electronic device (e.g., device 600) further determines whether thecontact satisfies one or more first criteria (706), such as in FIGS.6A-6B and 6G-6I. In some embodiments, the one or more criteria aresystem user interface display criteria used to determine whether thetouch input should cause the display of one or more indications or hintsof a system user interface.

In some embodiments, in accordance with a determination that the touchinput satisfies first criteria wherein the first criteria include arequirement that the contact continues to be detected in a predefinedregion of the touch-sensitive surface for longer than a time threshold,the electronic device displays, on the display, a first indication thatfurther input of a first type detected at the touch sensitive surfacewill cause the device to display a first system user interface (708),such as in FIG. 6I.

In some embodiments, such as in FIG. 6G, the predefined region of thetouch sensitive surface is a top region (e.g., 616), of the touchsensitive surface (e.g., 604). In some embodiments, the predefinedregion is a bottom region (e.g., 618) of the touch sensitive surface. Insome embodiment, the top region is larger than the bottom region, suchas in FIG. 6G.

In some embodiments, such as in FIG. 6H, one of the system userinterface display criteria is a predefined threshold of minimum contactduration (e.g., 612), such as 100 ms, 300 ms, 500 ms, or 1 s. In someembodiments, such as in FIG. 6I, one criterion is the contact's maximumthreshold of movement on the touch screen; that is, if movement of thecontact during the duration does not exceed a maximum movement threshold(e.g., the contact continues to be detected in a predefined region ofthe touch sensitive surface during the time threshold), the contact isoptionally considered substantially stationary. In some embodiments,such as in FIG. 6KK, one criterion is the maximum intensity of thecontact during the contact duration (e.g., 622) such that if theintensity of the contact during the time threshold does not exceed anintensity threshold, the contact satisfies the intensity criterion. Insome embodiments, touch inputs that satisfy the one or more of criteriaare referred to as “touch and hold” inputs.

In some embodiments, the indication is a visual hint or other indicationthat a certain type of further input, such as a swipe or an increase inthe intensity of the contact provided by the user to the electronicdevice through the touch sensitive surface, will cause full display ofthe system user interface. In some embodiments, such as in FIG. 6I, theindication is visual, such as a graphical icon or an affordance on thedisplay (e.g., 611). In some embodiments, such as in FIG. 6I, theelectronic device optionally displays a portion of the system userinterface, such as a top or bottom portion of the system user interface(e.g., 614). In some embodiments, such as in FIG. 6I, the indicationfurther includes tactile feedback, such as a vibration of the electronicdevice. In some embodiments, the indication further includes audiofeedback, such as a beep.

In some embodiments, such as in FIG. 6VV, the system user interface thatthe electronic device will optionally display is a “notification center”that displays notifications associated with the system or withapplications installed on the electronic device (e.g., 615), and is auser interface of the operating system of the electronic device asopposed to being a user interface of a particular application on theelectronic device. In some embodiments, such as in FIG. 6N, the systemuser interface is a “system control center” that indicates one or moresystem statuses of the electronic device and allows changes to certainfunctionalities of the electronic device (e.g., 614). In someembodiments, such as in FIG. 6N, the system user interface includesaffordances that indicate the wireless connectivity (e.g., Wi-Fi,Bluetooth, or cellular connectivity) status and the remaining batterycharge level of the electronic device and that enable and disable thewireless connectivity and the low power operating mode of the electronicdevice.

In some embodiments, in accordance with a determination that the touchinput does not satisfy the first criteria, the electronic device forgoesdisplaying the first indication (710), such as in FIGS. 6B-6C. In someembodiments, such as in FIGS. 6B and 6C, where the first criteria arenot met, the touch input is not considered to be a “touch-and-hold”gesture. Some such exemplary touch inputs include taps, swipes, clicks,or contacts with intensity greater than an intensity threshold touches.In such circumstances, no system user interface indication is displayed.In some embodiments, such as in FIG. 6B, if such a touch input isdetected while the electronic device is displaying an application userinterface (e.g., 602), the touch input results in an action or inputassociated with the application (e.g., as shown in FIGS. 6B-6C, in afitness tracking application, a swipe gesture scrolls through variousworkout type affordances) rather than displaying the indication of thesystem user interface. In some embodiments, such as in FIG. 6PP, if sucha touch input (e.g., 606) is detected while the electronic device isdisplaying a watch face user interface (e.g., 602), the touch inputresults in changing the watch face or otherwise interacting with thewatch face rather than displaying the indication of the system userinterface, such as in FIGS. 6PP and 6QQ. The above-described manner ofdisplaying the system user interface indication in response to aparticular input allows the electronic device to provide the user moreexpedient access to the system user interface and easier control of thedevice (e.g., reducing the number of required steps to accomplish thetask by obviating the need to first exit the user interface of aninstalled application or a watch face and navigating to a system userinterface in order to access the system user interface), whichsimplifies the interaction between the user and the device and enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by performing actions with fewer inputs and withoutexiting the displayed app user interface), which additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, such as in FIGS. 6I and 6M, the electronic deviceoptionally displays (712) the first indication (e.g. 611) in accordancewith the determination that the touch input satisfies the first criteria(e.g., 606) regardless of whether the user interface is an applicationuser interface (e.g., 602 in FIG. 6I) or a wake screen of the electronicdevice (e.g., 602 in FIG. 6M). In other words, the visual hint or otherindication is optionally displayed in accordance with receiving a touchand hold input regardless of whether the touch and hold input isreceived in an application user interface or in a wake screen (e.g.,watch face) user interface. The above-described manner of providingaccess to a system user interface after receiving a touch and hold inputallows the electronic device to simplify required user inputs to accesssystem user interfaces of the electronic device, such as the controlcenter or the notification center of a smart watch, which enhances theoperability of the device, makes the user-device interface moreintuitive and efficient by reducing friction in the user experience(e.g., providing the user with an intuitive sensory guidance toaccessing the system user interface with fewer requisite steps andwithout first exiting an application user interface), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIG. 6J or FIG. 6VV, the first type offurther input is a swipe input (714). In some embodiments, such as inFIG. 6J or FIG. 6VV, the further input is received at the touchsensitive surface (e.g., 604) without first detecting liftoff of thecontact from the touch sensitive surface corresponding to the touchinput that satisfied the first criteria (e.g., as shown by time bar610). In some embodiments, such as in FIG. 6J or FIG. 6VV, the firsttype of further input is an upward or a downward swipe input,respectively; in other words, the further input includes movement of thecontact on the touch sensitive surface that exceeds a minimum movementspeed and/or distance threshold across the touch-sensitive surface froman edge of the touch-sensitive surface in an upward or a downwarddirection.

In some embodiments, such as in FIG. 6J or 6VV, while displaying thefirst indication (e.g., in FIG. 6I, the first indication 611 remainsdisplayed while contact 606 is maintained at the touch screen 604), theelectronic device optionally receives (716) a further input comprisingthe swipe input detected on the touch-sensitive surface (e.g., 606). Insome embodiments where the touch-and-hold gesture input is detected atthe top region of the touch sensitive surface, the further input of thefirst type is a downward swipe (e.g. in FIG. 6VV, contact 606 startingfrom the top region of the touch sensitive surface across the touchsensitive surface). In some embodiments where the touch and hold gestureinput is detected at the bottom region of the touch sensitive surface(e.g., 604 in FIG. 6J), the further input of the first type is an upwardswipe (e.g., 606 in FIGS. 6J and 6K starting from the bottom region ofthe touch sensitive surface across the touch sensitive surface).

In some embodiments, such as in FIGS. 6J-6K and 6UU-6VV, in response toreceiving the further input, the electronic device displays (718), onthe display, the first system user interface. In some embodiments, inresponse to receiving the further input of the first type (e.g., a swipeinput shown in FIGS. 6J and 6K), the electronic device displays thefirst system user interface (e.g., 614 in FIG. 6K) on the display (e.g.,604 in FIG. 6K). In some embodiments, the first system user interface(e.g., 614 in FIG. 6K) is the full display of the system user interfacecorresponding to the visual hint or other indication (e.g., 614 in FIG.6J). The above-described manner of displaying the system user interfaceallows the electronic device to provide the user more expedient accessto the system user interface and easier control of the device (e.g.,without the need to first exit the user interface of an installedapplication and navigating to a system user interface to perform theaction), which simplifies the interaction between the user and thedevice and makes the user-device interface more efficient (e.g., byperforming actions with fewer inputs and without exiting the displayedapp user interface), which additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, such as in FIG. 6K, the first system user interfaceoptionally comprises one or more system affordances for controlling oneor more functions of the electronic device (720). In some embodiments,the system user interface includes one or more affordances that indicateone or more system statuses of the electronic device and allow changesto certain functionalities of the electronic device. For example, insome embodiments the system user interface (e.g., 614 in FIG. 6K)includes affordances (e.g., “battery level”, “Wi-Fi status”, etc.) thatindicate the wireless connectivity (e.g., Wi-Fi, Bluetooth, or cellularconnectivity) status and the remaining battery charge level of theelectronic device and that enable and disable the wireless connectivityand the low power operating mode of the electronic device. In this way,affordances for controlling functions on the electronic device arereachable from the user interface that was being displayed on theelectronic device before the touch-and-hold gesture was detected. Theabove-described manner of providing the user with access to systemcontrol functions of the electronic device after receiving a touch andhold input allows the electronic device to offer the user more directaccess to system control functions of the electronic device, whichenhances the operability of the device, makes the user-device interfacemore intuitive and efficient by reducing friction in the user experience(e.g., providing the user with an intuitive sensory guidance toaccessing the system user interface with fewer requisite steps andwithout first exiting an application user interface), which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIG. 6VV, the first system userinterface optionally comprises one or more representations of one ormore notifications at the electronic device (722). In some embodiments,the system user interface (e.g., 615) includes one or morerepresentations of system or application notifications (e.g.,“Notification 1”, etc.) such as a notification of receiving a socialmedia message from an installed social media application or anotification about an upcoming meeting in a system from a systemcalendar function. In this way, information about notifications on theelectronic device is reachable from the user interface that was beingdisplayed on the electronic device before the touch-and-hold gesture wasdetected. The above-described manner of providing user with access to avisual list of notifications received at the electronic device afterreceiving a touch and hold input allows the electronic device to offerthe user more direct access to the notifications, which enhances theoperability of the device, makes the user-device interface moreintuitive and efficient by reducing friction in the user experience(e.g., reducing the required input steps to access the list ofnotifications and obviating the need to first exiting an applicationuser interface), which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, such as in FIG. 6RR, while displaying the firstsystem user interface with the one or more system affordances (e.g.,614), the electronic device optionally receives (724) a second touchinput comprising a second contact (e.g., 606) detected on thetouch-sensitive surface. In some embodiments, the second contact is partof a tap input used to change the functionality of the electronicdevice, such as enabling and disabling wireless connectivity andlow-power operating mode. In some embodiments, the second contact ispart of a swipe input used to scroll through the system user interfaceto display other affordances. In some embodiments, the second contact ispart of a touch-and-hold input.

In some embodiments, such as in FIGS. 6RR and 6SS, in response toreceiving the second touch input (e.g., 606), and in accordance with adetermination that the second touch input satisfies second criteria(726) the electronic device optionally operates (728) the first systemuser interface (e.g., 614) in a reconfiguration mode in which the one ormore system affordances are repositionable relative to other systemaffordances.

In some embodiments, such as in FIGS. 6RR and 6SS, the second contact isa touch and hold input. In some embodiments, the minimum contactduration and/or the maximum contact intensity to qualify as the touchand hold input here are the same as the minimum contact duration and themaximum contact intensity of the touch and hold input that results inthe display of the indication of the system user interface. In someembodiments, the minimum contact duration and/or the maximum contactintensity are different than the minimum contact duration and themaximum contact intensity of the touch and hold input that results inthe display of the indication of the system user interface.

In some embodiments, such as in FIGS. 6RR and 6SS, after determiningthat the second touch input received is a touch and hold input, thesystem user interface enters a reconfiguration mode, in which theselectable system affordances can be repositioned and rearranged in thesystem user interface. In some embodiments, the reconfiguration mode isindicated by one or more visual indications. For example, in oneembodiment, the selectable user interface objects jiggle as though theyare floating on water (e.g., each respective selectable systemaffordance oscillates about a respective average position of theselectable system affordance on the display. Rearranging the systemaffordances is optionally accomplished by, after entering and while inthe reconfiguration mode, detecting touchdown on and dragging of asystem affordance to a new position in the first system user interface);

In some embodiments, in response to receiving the second touch input,and in accordance with a determination that the second touch input doesnot satisfy the second criteria, the electronic device optionallyoperates (730) the first system user interface in a standard mode inwhich the one or more system affordances are not repositionable relativeto other system affordances (e.g., the user is not able to touch anddrag the affordances to new positions in the first system userinterface). The above-described manner of reconfiguring the system userinterface allows the user a simple manner to configure their preferredarrangement and access to the system user interface and easier controlof the device, which allows greater customization of interaction betweenthe user and the device, provides a more personalized user experience,reduces cognitive load and distraction, and enhances safety andconvenience while interacting with the electronic device (e.g., whilerunning or performing other tasks), which simplifies the interactionbetween the user and the device and makes the user-device interface moreefficient (e.g., by performing actions with fewer inputs), whichadditionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIG. 6A-6E, in response to receiving thetouch input and in accordance with the determination that the touchinput does not satisfy the first criteria, and in accordance with theuser interface being an application user interface, the electronicdevice performs (734) an operation in the application user interface inaccordance with the touch input (732). In some embodiments, the touchinput does not satisfy the first criteria because the contact occursoutside of the predefined regions on the touch sensitive surface, theduration of the touch input does not exceed the minimum threshold (e.g.,a tap input), the intensity of the touch input exceeds the maximumthreshold (e.g., a hard press input), or the touch input includesmovements that exceed the maximum movement threshold (e.g. a swipeinput).

In some embodiments, such as in FIGS. 6A-6C where the user interface isa user interface of a fitness application (602), receiving a swipe inputwhile displaying the fitness application user interface results inscrolling through the list of available workout type affordances. Inanother embodiment, such as in FIGS. 6D and 6E, receiving a tap inputwhile displaying the fitness application user interface results ininvoking an affordance corresponding to the location on the touchsensitive surface where the tap input was received (e.g., start anoutdoor run workout or start an outdoor cycle workout).

In some embodiments, such as in FIGS. 6L-6N, in response to receivingthe touch input and in accordance with the determination that the touchinput does not satisfy the first criteria, and in accordance with theuser interface being a wake screen user interface (e.g., 602) (736), andin accordance with a determination that the touch input includes a swipeinput, the electronic device displays (738), on the display, the firstsystem user interface. In some embodiments, such as in FIGS. 6L-6N, ifthe user interface is a wake screen (e.g., watch face) user interface(e.g., 602) instead of an application user interface, the system furtherdetermines whether the non-touch and hold input is a swipe input. If theinput is determined to be a swipe input, such as an upward or a downwardswipe input (e.g., upward swipe in in 6M and 6N), the system in responseoptionally displays the first system user interface (e.g., 614). Assuch, on the wake screen user interface, the first system user interfaceis reachable via the touch-and-hold input described above, or via merelyan upward or downward swipe input detected on the wake screen (e.g.,without performing a touch-and-hold). In such circumstances, the firstsystem user interface is optionally displayed without first displayingthe indication of the first system user interface. Further, in someembodiments, a horizontal swipe input does not display the first systemuser interface, but rather performs a different action with respect tothe wake screen user interface (e.g., switches from displaying one watchface to displaying another watch face).

In some embodiments, such as in FIGS. 6W and 6X, in response toreceiving the touch input (736), and in accordance with a determinationthat the touch input does not include a swipe input, the electronicdevice performs (740) an operation in the watch face user interface inaccordance with the input. In other words, if the input is not a swipeinput (e.g., the input is a tap input or a hard press), the deviceoptionally performs an operation in accordance with the input. Forexample, a tap input received on an affordance in the watch face userinterface optionally triggers the affordance on the watch face. Theabove-described manner of providing the user access to the system userinterface allows the user another simple and efficient way to access thesystem user interface and easier control of the device, enhances safetyand convenience while interacting with the electronic device (e.g.,while running or performing other tasks), simplifies the interactionbetween the user and the device and makes the user-device interface moreefficient (e.g., by performing actions with fewer inputs), andadditionally reduces power usage and improves battery life of the deviceby enabling the user to use the device more quickly and efficiently.

In some embodiments, such as in FIGS. 6W and 6X, in response toreceiving the touch input and in accordance with the determination thatthe user interface is the wake screen (e.g., watch face) user interfaceand that the touch input does not include a swipe input (742), andfurther in accordance with a determination that the touch input is a tapinput, the electronic device performs (744) an operation in the wakescreen user interface in accordance with the tap input. In other words,in some embodiments such as in FIGS. 6W and 6X, where a wake screen(e.g., watch face) user interface (602) is displayed while a first touchinput (606) that is received is neither a touch and hold input nor aswipe input, the system further determines whether the input is a tapinput. If the input is determined to be a tap input, the electronicdevice optionally performs an operation consistent with detecting a tapinput (e.g., a tap input (606) received on an affordance (e.g.,stopwatch affordance) in the watch face user interface (602) optionallytriggers the affordance on the watch face (e.g., show a stopwatchapplication user interface, as shown in FIG. 6X)). The above-describedmanner of receiving and processing user touch inputs enables theelectronic devices to respond to a variety of different touch gestureinputs in both an application user interface and a wake screen userinterface while still allowing efficient access to a system userinterface (including all the associated benefits such as reducedcognitive friction, less distraction, and longer battery life) whilemaintaining the user's interactive experience with the wake screen userinterface when the user provides a tap input to the wake screen userinterface (thereby reducing cognitive dissonance associated withunfamiliar or unexpected wake screen user interface responses), whichsimplifies the interaction between the user and the device and makes theuser-device interface more efficient (e.g., by performing actions withfewer inputs), and additionally reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, such as in FIGS. 6D and 6E, in response toreceiving the touch input and in accordance with the determination thatthe user interface is an application user interface (746), and inaccordance with a determination that the touch input is a tap input, theelectronic device performs (748) an operation in the application userinterface in accordance with the tap input. In some embodiments where anapplication (e.g., a fitness application) interface is displayed, suchas in FIGS. 6D and 6E, while a first touch input (606) that is receivedis neither a touch and hold input nor a swipe input, the electronicdevice (600) further determines whether the input is a tap input. If theinput is determined to be a tap input, an operation consistent withdetecting a tap input, such as performing an operation (e.g., starting,pausing, or stopping a workout session) associated with a tappedapplication affordance (e.g., the outdoor walk affordance associatedwith starting an outdoor walk workout session) is optionally performed.The above-described manner of receiving and processing user touch inputsenables the electronic devices to respond to a variety of differenttouch gesture inputs in both an application user interface and a wakescreen user interface while still allowing efficient access to a systemuser interface (including all the associated benefits such as reducedcognitive friction, less distraction, and longer battery life) whilemaintaining the user's interactive experience with the displayedapplication user interface when the user provides a tap input to theapplication (thereby reducing cognitive dissonance associated withunfamiliar or unexpected application user interface responses), whichsimplifies the interaction between the user and the device and makes theuser-device interface more efficient (e.g., by performing actions withfewer inputs), and additionally reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, such as in FIGS. 6Q and 6U, while displaying thefirst indication (611) that further input of the first type detected atthe touch sensitive surface will cause the device to display the firstsystem user interface, the electronic device optionally detects (750)liftoff of the contact from the touch-sensitive surface (instead of afurther input). In some embodiments, such as in FIGS. 6Q-6R and 6T-6U,in response to detecting the liftoff of the contact, the electronicdevice ceases displaying (752) the first indication without performingan operation in the user interface, and reverts the displayed userinterface to the appearance before the touch and hold input was detected(e.g., any obscured portions of the user interface reappear, and if thesize of the user interface was reduced proportionally while displayingthe indication, the user interface reverts to its original size). Theabove-described manner of accessing and displaying the system userinterface allows the electronic device to provide the user a moreexpedient way to cancel the display of system user interface indicationand return to the application or wake screen (e.g., without needingadditional inputs to remove the system user interface indication), whichsimplifies the interaction between the user and the device and makes theuser-device interface more cognitively efficient (e.g., by performingactions with fewer inputs), which additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, such as in FIG. 6H, in accordance with thedetermination that the touch input satisfies the first criteria, theelectronic device generates (754), at the electronic device, a tactileoutput corresponding to the touch input satisfying the first criteria.In some embodiments, such as in FIG. 6H, the tactile feedback is avibration of the electronic device, which the device generates when thetouch-and-hold gesture is detected and the indication of the firstsystem user interface is displayed. The above-described manner ofproviding tactile feedback to the user allows the electronic device tomore effectively communicate to the user that further input will causedisplay of the first system user interface, which simplifies theinteraction between the user and the device and makes the user-deviceinterface more efficient (e.g., by performing actions with fewerinputs), which additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, such as in FIG. 6G, the predefined region of thetouch-sensitive surface comprises a top region or a bottom region of thetouch sensitive surface (756). In some embodiments, such as in FIG. 6G,the predefined region includes a top region (e.g., 616) and/or a bottomregion (e.g., 618) of the touch sensitive surface (e.g., 604), where thetop and the bottom regions are defined relative to the orientation inwhich the user interacts with the display (e.g., the orientation oftexts being displayed in an application user interface or theorientation of a simulated analog watch dial complication beingdisplayed on the watch face). In some embodiments, a touch-and-holdinput detected in a region of the touch-sensitive surface other than thetop or bottom regions (e.g., in a middle region of 604) will not causedisplay of the indication of the first system user interface. Theabove-described manner of accessing and displaying the system userinterface enables the electronic devices to distinguish and providedifferent responses to touch gesture inputs detected at differentlocations on the touch sensitive screen in both an application userinterface and a wake screen user interface, while still allowingefficient access to a system user interface (including all theassociated benefits such as reduced cognitive friction, lessdistraction, and longer battery life), which maintains the user'sinteractive experience with the displayed application or wake screenuser interface (thereby reducing cognitive dissonance associated withunfamiliar or unexpected application user interface responses).

In some embodiments, such as in FIG. 6G, the top region of the touchsensitive surface is larger than the bottom region of the touchsensitive surface (758). In some embodiments, the top region of thetouch sensitive surface is larger than the bottom region of the touchsensitive surface. In some embodiments, this is the case becausetouching the top region of the touch-sensitive surface is optionallyharder for a user than is touching the bottom region of thetouch-sensitive surface (e.g., when the touch-sensitive surface is awatch touch screen on a user's left wrist, it is optionally easier forthe user to target a smaller area with their right finger on the bottomregion of the watch touch screen, which is closer to the user's rightfinger, than for the user to target an area with their right finger onthe top region of the watch touch screen, which is further from theuser's right finger. The above-described manner of making the top regionlarger than the bottom region allows the electronic device to provideeasy access to both the notification center and the control center userinterfaces, which makes the user-device interface more efficient, whichfurther reduces power usage and improves battery life of the device byenabling the user to use the device more quickly and efficiently.

In some embodiments, such as in FIG. 6WW, in accordance with adetermination that the electronic device is configured for operating ona first hand of a user, the top region of the touch-sensitive surface(e.g., 616) is located at a first position on the electronic device andthe bottom region of the touch-sensitive surface (e.g., 618) is locatedat a second position on the electronic device (760). In someembodiments, such as in FIG. 6XX, in accordance with a determinationthat the electronic device is configured for operating on a second handof the user, different than the first hand, the top region of thetouch-sensitive surface (e.g., 616) is located at the second position onthe electronic device and the bottom region of the touch-sensitivesurface (e.g., 618) is located at the first position on the electronicdevice (762). Thus, in an embodiment where the electronic device is awrist-worn smart watch, the top region refers to the region closest tothe pinky side of the wrist (e.g., the top region of the screen while auser raises her wrist to view the screen), and the bottom region refersto the thumb side of the wrist (e.g., the bottom region of the screenwhile a user raises her wrist to view the screen). Therefore, in someembodiments the top region and the bottom region change depending on thehandedness of the electronic device (e.g., a wrist-worn smart watch).Where the watch is configured for left-handed wear (e.g., worn on theright wrist), the top region refers to the physical position or regionclose to the bottom region in a right-handed wearing configuration, andvice versa. The above-described manner of accessing and displaying thesystem user interface enables the electronic device to provide the sameresponses to a touch and hold input gestures regardless whether theelectronic device is operating in a left-handed configuration or aright-handed configuration, which makes the user-device interface moreefficient, which further reduces power usage and improves battery lifeof the device by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIGS. 6J and 6K, in accordance with adetermination that the contact is detected in the bottom region of thetouch-sensitive surface, the first system user interface comprises oneor more system affordances for controlling one or more functions of theelectronic device (764). In some embodiments, such as in FIGS. 6UU and6VV, in accordance with a determination that the contact (e.g., 606) isdetected in the top region of the touch-sensitive surface (e.g., 616),the first system user interface (e.g., 615) comprises one or morerepresentations of one or more notifications at the electronic device(766) In some embodiments, such as in FIGS. 6UU and 6VV, if the touchand hold input (e.g., 606) is detected at the bottom region of the touchsensitive display (e.g., 616), the system user interface that will bedisplayed (e.g., 615) with the further input (e.g., a swipe) is the“notification center” that displays representations for notificationsassociated with the system or with applications installed on theelectronic device. In some embodiments, such as in FIGS. 6J and 6K, ifthe touch and hold input (e.g., 606) is detected at the bottom region ofthe touch sensitive display (e.g., 618), the system user interface thatwill be displayed (e.g., 614) with the further input (e.g., a swipe) isthe system control center with one or more affordances that indicate oneor more system statuses and control one or more functionalities of theelectronic device). The above-described manner of accessing anddisplaying the system user interface allows the electronic device toprovide different system user interfaces in response to touch and holdinputs detected at different locations on the touch sensitive screen,which enables the user more expedient access to more functionalities ofthe electronic device, complete more tasks with few input steps, whichmakes the user-device interface more efficient, which further reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, in accordance with the determination that the touchinput does not satisfy the first criteria because the contact wasdetected outside of the top and bottom regions of the touch-sensitivesurface, the electronic device performs (768) an operation in the userinterface in accordance with the touch input, such as in FIG. 6PP. Insome embodiments, the location of the detected touch input (e.g., a tapor a touch and hold input) is outside the predefined region of the touchsensitive surface (e.g., the top and bottom regions of the touchsensitive display), and the electronic device responds to thisoutside-the-region touch input according to how the user interface thatis displayed when the touch input is received is configured to respondto the touch input. For example, a tap in the center region of thetouch-sensitive surface optionally causes selection of an affordance inthe user interface, a touch and hold input in the center region of thetouch-sensitive surface optionally causes initiation of a process in theuser interface, etc. The above-described manner of processing non-topand bottom region touches in accordance with the displayed userinterface allows the electronic device to respond to a variety ofdifferent touch gesture inputs in both an application user interface anda wake screen user interface while still allowing efficient access to asystem user interface (including all the associated benefits such asreduced cognitive friction, less distraction, and longer battery life)while maintaining the user's interactive experience with the displayedapplication user interface, which simplifies the interaction between theuser and the device and makes the user-device interface more efficient(e.g., by performing actions with fewer inputs), and additionallyreduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

In some embodiments, such as in FIG. 6BB, while displaying the userinterface on the display, the electronic device receives (770), via thetouch-sensitive surface, an indication of an object detected near thetouch-sensitive surface but not on the touch-sensitive surface (e.g., afinger resting on the top or bottom edge of the device 600, near the topor bottom regions (e.g., 616 and 618) of the touch-sensitive surface(e.g., 604), but not on the touch-sensitive surface).

In some embodiments, such as in FIG. 6CC, in response to receiving theindication of the object and in accordance with a determination that theobject satisfies second criteria, wherein the second criteria include arequirement that the object continues to be detected near the top orbottom regions of the touch-sensitive surface, but not on thetouch-sensitive surface, for longer than the time threshold, theelectronic device displays (772), on the display, the first indicationthat further input of the first type detected at the touch sensitivesurface will cause the device to display the first system userinterface.

In some embodiments, such as in FIG. 6CC, if the touch and hold input isdetected near the top or the bottom edge of the touch sensitive surface(e.g., 604) but not directly on the touch-sensitive surface, theelectronic device displays the same visual hint or other indication(e.g., 611 and/or vibration, audio beep, etc.) that a certain type offurther input, such as a swipe provided by the user to the electronicdevice through the touch sensitive surface, will cause full display ofthe system user interface (e.g., 614). In other words, a touch and holdinput near the top edge but not on the touch sensitive displayoptionally results in the display of the same indication as a touch andhold input in the top region of the touch sensitive display (e.g., 615in FIG. 6UU), and a touch and hold input near the bottom edge but not onthe touch sensitive display optionally results in the display of thesame indication as a touch and hold input in the bottom region of thetouch sensitive display (e.g., 614 in FIG. 6J). In some embodiments, inaccordance with a determination that the object does not satisfy thesecond criteria, the electronic device forgoes displaying the firstindication that further input of the first type detected at thetouch-sensitive surface will cause the device to display the firstsystem user interface. The above-described manner of accessing anddisplaying the system user interface allows the electronic system toprovide additional touch input location options to access the systemsuser interface, increases the sensitivity of the electronic device to areceived touch and hold input, which allows the user a simpler manner toaccess to the system user interface and easier control of the device,which in turn makes the user-device interface more efficient, reducesuser cognitive load and distraction, and reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In some embodiments, such as in FIG. 6J, in response to receiving thetouch input and in accordance with the determination that the touchinput satisfies the first criteria, the electronic device obscures (774)display of the user interface. In some embodiments, such as in FIG. 6J,in addition to displaying the indication of the system user interface(e.g., 611), the touch and hold input detected in the predefined region(e.g., 618) also results in obscuring of the user interface (e.g., 602)that was displayed before detecting the touch and hold input (e.g.,reducing the size of the user interface 602 proportionally whilemaintaining a constant aspect ratio of the user interface 602, and/orreplacing a portion of the displayed user interface 602 with theindication in accordance with the location of the detected touch andhold input to achieve a visual effect where the user interface is being“covered up” by the system user interface indication, and/or fading outor darkening the user interface). The above-described manner ofproviding visual feedback associated with the indication of the systemuser interface allows the electronic device to provide the user with anadditional visual feedback to ascertain that a gesture input hasachieved its intended purpose, which allows the electronic device tomore effectively communicate with the user, which simplifies theinteraction between the user and the device and makes the user-deviceinterface more efficient (e.g., by performing actions with fewerinputs), which additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, such as in FIGS. 6FF and 6GG, the first type offurther input comprises an increase in an intensity of the contact abovean intensity threshold (776). In some embodiments, such as in FIGS. 6FFand 6GG, the first type of further input is a hard press; that is, theintensity of the input (e.g. the downward pressure of the contactagainst the touch-sensitive surface) increases to exceed a predefinedintensity threshold 622 after the touch-and-hold input has beendetected.

In some embodiments, such as in FIGS. 6II and 6JJ, while displaying thefirst indication (in some embodiments, the first indication remainsbeing displayed while contact is maintained at the touch sensitivesurface), the electronic device receives (778) a further inputcomprising the increase of the intensity of the contact (e.g., 620)above the intensity threshold (e.g., 622) (e.g., the further input isthe hard press described above). In some embodiments, such as in FIGS.6II and 6JJ, in response to receiving the further input, the electronicdevice displays (780), on the display, the first system user interface.In other words, in some embodiments, such as in FIGS. 6II and 6JJ, inresponse to receiving a hard press input, the system displays the systemuser interface on the display; in some embodiments, the system userinterface is the full display of the system user interface correspondingto the visual hint or other indication (e.g., a different system userinterface depending on whether the touch-and-hold and subsequent hardpress were detected in the top region or the bottom region of thetouch-sensitive surface, as described above). In some embodiments, ifthe electronic device detects liftoff of the contact before theintensity of the contact reaches the intensity threshold (e.g., withoutthe intensity of the contact reaching the intensity threshold), theelectronic device forgoes displaying the first system user interface andceases displaying the first indication without performing an operationin the user interface. The above-described manner of displaying thesystem user interface allows the electronic device to provide the usermore expedient access to the system user interface and easier control ofthe device by allowing an additional input gesture method for accessingthe system user interface, which simplifies the interaction between theuser and the device and enhances the operability of the device and makesthe user-device interface more efficient (e.g., by performing actionswith fewer inputs and without exiting the displayed app user interface),which additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIG. 6GG, in accordance with thedetermination that the touch input satisfies the first criteria, theelectronic device generates (782), at the electronic device, a firsttactile output corresponding to the touch input satisfying the firstcriteria, and in response to receiving the further input, the electronicdevice generates (784), at the electronic device, a second tactileoutput corresponding to the intensity of the contact increasing abovethe intensity threshold, such as in FIG. 6II. In other words, in someembodiments, such as in FIGS. 6FF-6JJ, tactile feedback is providedtwice by the electronic device: once when the indication of the firstsystem user interface is displayed in response to the touch-and-holdinput (such as in FIG. 6GG), and another time when the intensity of thecontact exceeds the intensity threshold and the full first system userinterface is displayed (such as in FIG. 6II). Thus, while the systemuser interface indication is displayed, detecting a hard press on thetouch sensitive surface (e.g., a touch sensitive display) optionallyresults in a further tactile feedback, such as a vibration of theelectronic device. The above-described manner of providing tactilefeedback to the user allows the electronic device to provide additionaluser feedback, assuring the user that an intended input to theelectronic device was accomplished, thereby reducing cognitive loadassociated with interacting with the device, which makes the user-deviceinterface more efficient, which further reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently. Additionally, the tactile feedback increasesaccessibility of the electronic device by users with certain physical(e.g., audio-visual) impairments.

In some embodiments, such as in FIG. 6KK, in response to receiving thetouch input (786), and in accordance with a determination that the touchinput satisfies second criteria, wherein the second criteria include arequirement that the contact is detected in the predefined region of thetouch-sensitive surface and that an intensity of the contact exceeds anintensity threshold before the time threshold in order for the secondcriteria to be met, such as in FIG. 6LL, the electronic device displays(788), on the display, the first system user interface withoutdisplaying the first indication that further input of the first typedetected at the touch sensitive surface will cause the device to displaythe first system user interface such as in FIGS. 6LL and 6MM. In otherwords, in some embodiments, receiving a hard press (e.g., 606 in FIG.6LL, a stationery contact having an intensity greater than an intensitythreshold) instead of a touch and hold input in the predefined region ofthe touch sensitive surface results in displaying the system userinterface without displaying the indication that a further input willcause the device to display the system user interface. For example, ahard press detected on the top region of the touch sensitive displayresults in displaying the notification center user interface, while ahard press detected on the bottom region of the touch sensitive displayresults in displaying the control center user interface. In someembodiments, such hard presses display their resulting system userinterfaces without waiting for the touch-and-hold time threshold to besatisfied. The above-described manner of displaying the system userinterface allows the electronic device to provide the user moreexpedient access to the system user interface and easier control of thedevice (e.g., without the need to first wait for the system userinterface indication), which simplifies the interaction between the userand the device and enhances the operability of the device and makes theuser-device interface more efficient (e.g., by performing actions withfewer inputs and without exiting the displayed app user interface),which additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, such as in FIGS. 6PP and 6QQ, in response toreceiving the touch input (790) and in accordance with a determinationthat the touch input does not satisfy the first criteria or the secondcriteria because the contact is detected outside of the predefinedregion of the touch-sensitive surface, and that the intensity of thecontact exceeds the intensity threshold, the electronic device displays(792), on the display, a second user interface, not the first systemuser interface, associated with the first user interface. In otherwords, in some embodiments, such as in FIGS. 6PP and 6QQ, if a hardpress is detected in the center region (e.g., outside 616 and 618) ofthe touch sensitive surface (e.g., 604) while the electronic device isdisplaying a watch face user interface (e.g., 602), the hard press(e.g., 606) is neither a touch and hold input (thus failing to satisfythe criteria associated with detecting a touch and hold input) nordetected in the predefined region on the touch sensitive surface (thusfailing to satisfy the criteria associated with detecting a input in thepredefined region). As a result, the electronic device optionallydisplays a watch face editing user interface (e.g., a user interfacethat allows the user to scroll through watch faces and/or edit thosewatch faces). The above-described manner of interacting with the watchface user interface allows the user easier access and reconfiguration ofdifferent watch face user interfaces, simplifies the interaction betweenthe user and the device and enhances the operability of the device andmakes the user-device interface more efficient (e.g., by performingactions with fewer inputs and without exiting the displayed app userinterface), which additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, such as in FIG. 6LL, in response to receiving thetouch input and in accordance with the determination that the touchinput satisfies the second criteria, the electronic device generates(794), at the electronic device, a tactile output corresponding to theintensity of the contact increasing above the intensity threshold. Inother words, in some embodiments, such as in FIG. 6LL, receiving a hardpress instead of a touch and hold input (e.g., 606) in the predefinedregions (e.g., 616 or 618) of the touch sensitive surface that resultsin displaying the full first system user interface (e.g., 614) alsoresults in the electronic device generating a tactile feedback, such asa vibration of the electronic device, when the intensity of the contactreaches the intensity threshold (e.g., 622) and the full first systemuser interface is displayed, as shown in Fig. MM. The above-describedmanner of providing tactile feedback to the user allows the electronicdevice to provide additional user feedback, assuring a user that anintended input to the electronic device was accomplished, therebyreducing cognitive load associated with interacting with the device,which makes the user-device interface more efficient, which furtherreduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently. Additionally,the tactile feedback increases accessibility of the electronic device byusers with certain physical (e.g., audio-visual) impairments.

It should be understood that the particular order in which theoperations in FIGS. 7A-7H have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. The operations in the information processing methods describedabove are, optionally, implemented by running one or more functionalmodules in an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A-1B, 3, 5A-5H) orapplication specific chips. Further, the operations described above withreference to FIGS. 7A-7H are, optionally, implemented by componentsdepicted in FIGS. 1A-1B. For example, displaying operations 702, 708 and710, and receiving operation 704 are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch screen 604, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on the touchscreen corresponds to a predefined event or sub-event, such as selectionof an object on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content (e.g.,health and fitness related content) that may be of interest to them. Thepresent disclosure contemplates that in some instances, this gathereddata may include personal information data that uniquely identifies orcan be used to contact or locate a specific person. Such personalinformation data can include demographic data, location-based data,telephone numbers, email addresses, twitter ID's, home addresses, dataor records relating to a user's health or level of fitness (e.g., vitalsigns measurements, medication information, exercise information), dateof birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables users tocalculated control of the delivered content. Further, other uses forpersonal information data that benefit the user are also contemplated bythe present disclosure. For instance, health and fitness data may beused to provide insights into a user's general wellness, or may be usedas positive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof health or fitness-related services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide health-associated data for targetedcontent delivery services. In yet another example, users can select tolimit the length of time health-associated data is maintained orentirely prohibit the development of a baseline health or fitnessprofile. In addition to providing “opt in” and “opt out” options, thepresent disclosure contemplates providing notifications relating to theaccess or use of personal information. For instance, a user may benotified upon downloading an app that their personal information datawill be accessed and then reminded again just before personalinformation data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publicly available information.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at an electronic device incommunication with a display and a touch-sensitive surface: displaying,via the display, a user interface; while displaying the user interfacevia the display, receiving a touch input detected at a respectivelocation on the touch-sensitive surface, wherein the user interfaceincludes a respective user interface element at a location in the userinterface that corresponds to the respective location on thetouch-sensitive surface; and in response to receiving the touch input:in accordance with a determination that the touch input satisfies one ormore first criteria, wherein the one or more first criteria include arequirement that the contact continues to be detected at the respectivelocation of the touch-sensitive surface for longer than a timethreshold: in accordance with a determination that the respectivelocation is within a first region of the touch-sensitive surfacecorresponding to a first region of the user interface, displaying, viathe display, a first indication of a first system user interface withoutdisplaying a second indication of a second system user interface,different than the first system user interface, and without interactingwith the respective user interface element; and in accordance with adetermination that the respective location is within a second region,different than the first region, of the touch-sensitive surfacecorresponding to a second region, different than the first region, ofthe user interface, displaying, via the display, the second indicationof the second system user interface, without displaying the firstindication and without interacting with the respective user interfaceelement.
 2. The method of claim 1, wherein the electronic devicedisplays the first indication or the second indication regardless ofwhether the user interface is an application user interface or a wakescreen of the electronic device.
 3. The method of claim 1, wherein thefirst indication is an indication that further input of a first typedetected at the touch sensitive surface will cause the device to displaythe first system user interface, and the second indication is anindication that further input of the first type detected at the touchsensitive surface will cause the device to display the second systemuser interface.
 4. The method of claim 3, wherein the first type offurther input is a swipe input, the method further comprising: whiledisplaying the first indication, receiving a first further inputcomprising a first swipe input detected on the touch-sensitive surface;in response to receiving the first further input, displaying, on thedisplay, the first system user interface; while displaying the secondindication, receiving a second further input comprising a second swipeinput detected on the touch-sensitive surface; and in response toreceiving the second further input, displaying, on the display, thesecond system user interface.
 5. The method of claim 4, wherein thefirst swipe input is in a different direction than the second swipeinput.
 6. The method in claim 3, wherein the first type of further inputcomprises an increase in an intensity of the contact above an intensitythreshold, the method further comprising: in accordance with adetermination that the first indication is displayed: while displayingthe first indication, receiving a first further input comprising anincrease of the intensity of the contact above the intensity threshold;in response to receiving the first further input, displaying, on thedisplay, the first system user interface; and in accordance with adetermination that the second indication is displayed: while displayingthe second indication, receiving a second further input comprising anincrease of the intensity of the contact above the intensity threshold;and in response to receiving the second further input, displaying, onthe display, the second system user interface.
 7. The method in claim 6,further comprising: in accordance with the determination that the touchinput satisfies the one or more first criteria, generating, at theelectronic device, a first tactile output corresponding to the touchinput satisfying the one or more first criteria; in response toreceiving the first further input, generating, at the electronic device,a second tactile output corresponding to the intensity of the contactincreasing above the intensity threshold; and in response to receivingthe second further input, generating, at the electronic device, a thirdtactile output corresponding to the intensity of the contact increasingabove the intensity threshold.
 8. The method of claim 1, wherein thefirst system user interface comprises one or more system affordances forcontrolling one or more functions of the electronic device, and thesecond system user interface comprises one or more representations ofone or more notifications at the electronic device.
 9. The method inclaim 1, further comprising in response to receiving the touch input andin accordance with a determination that the touch input does not satisfythe one or more first criteria: in accordance with the user interfacebeing an application user interface, performing an operation in theapplication user interface in accordance with the touch input; and inaccordance with the user interface being a wake screen user interface:in accordance with a determination that the touch input includes a swipeinput, displaying, on the display, the first system user interface orthe second system user interface; and in accordance with a determinationthat the touch input does not include a swipe input, performing anoperation in the wake screen user interface in accordance with theinput.
 10. The method of claim 9, wherein: performing an operation inthe application user interface includes, in accordance with adetermination that the touch input is a tap input, interacting with therespective user interface element, and performing an operation in thewake screen user interface in accordance with the input includes, inaccordance with the determination that the touch input is a tap input,interacting with the respective user interface element.
 11. The methodin claim 1, further comprising: while displaying the first indication,detecting liftoff of the contact from the touch-sensitive surface; andin response to detecting the liftoff of the contact, ceasing displayingthe first indication without performing an operation in the userinterface.
 12. The method of claim 11, further comprising: whiledisplaying the second indication, detecting liftoff of a contact fromthe touch-sensitive surface; and in response to detecting the liftoff ofthe contact, ceasing displaying the second indication without performingan operation in the user interface.
 13. The method of claim 1, furthercomprising in accordance with the determination that the touch inputsatisfies the one or more first criteria, generating, at the electronicdevice, a tactile output corresponding to the touch input satisfying theone or more first criteria.
 14. The method of claim 1, wherein: inaccordance with a determination that the electronic device is configuredfor operating on a first hand of a user, the first region of thetouch-sensitive surface is located at a first position on the electronicdevice and the second region of the touch-sensitive surface is locatedat a second position on the electronic device, and in accordance with adetermination that the electronic device is configured for operating ona second hand of the user, different than the first hand, the firstregion of the touch-sensitive surface is located at the second positionon the electronic device and the second region of the touch-sensitivesurface is located at the first position on the electronic device. 15.The method of claim 1, further comprising in response to receiving thetouch input and in accordance with the determination that the touchinput satisfies the one or more first criteria, obscuring display of theuser interface.
 16. An electronic device, comprising: one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying, via a display, a user interface; while displaying theuser interface via the display, receiving a touch input detected at arespective location on a touch-sensitive surface, wherein the userinterface includes a respective user interface element at a location inthe user interface that corresponds to the respective location on thetouch-sensitive surface; and in response to receiving the touch input:in accordance with a determination that the touch input satisfies one ormore first criteria, wherein the one or more first criteria include arequirement that the contact continues to be detected at the respectivelocation of the touch-sensitive surface for longer than a timethreshold: in accordance with a determination that the respectivelocation is within a first region of the touch-sensitive surfacecorresponding to a first region of the user interface, displaying, viathe display, a first indication of a first system user interface withoutdisplaying a second indication of a second system user interface,different than the first system user interface, and without interactingwith the respective user interface element; and in accordance with adetermination that the respective location is within a second region,different than the first region, of the touch-sensitive surfacecorresponding to a second region, different than the first region, ofthe user interface, displaying, via the display, the second indicationof the second system user interface, without displaying the firstindication and without interacting with the respective user interfaceelement.
 17. A non-transitory computer readable storage medium storingone or more programs, the one or more programs comprising instructions,which when executed by one or more processors of an electronic device,cause the electronic device to perform: displaying, via a display, auser interface; while displaying the user interface via the display,receiving a touch input detected at a respective location on atouch-sensitive surface, wherein the user interface includes arespective user interface element at a location in the user interfacethat corresponds to the respective location on the touch-sensitivesurface; and in response to receiving the touch input: in accordancewith a determination that the touch input satisfies one or more firstcriteria, wherein the one or more first criteria include a requirementthat the contact continues to be detected at the respective location ofthe touch-sensitive surface for longer than a time threshold: inaccordance with a determination that the respective location is within afirst region of the touch-sensitive surface corresponding to a firstregion of the user interface, displaying, via the display, a firstindication of a first system user interface without displaying a secondindication of a second system user interface, different than the firstsystem user interface, and without interacting with the respective userinterface element; and in accordance with a determination that therespective location is within a second region, different than the firstregion, of the touch-sensitive surface corresponding to a second region,different than the first region, of the user interface, displaying, viathe display, the second indication of the second system user interface,without displaying the first indication and without interacting with therespective user interface element.